Jeff Layman <Je...@invalid.invalid> wrote
>> I hate to see other people struggling with Android - as it hurts me
>> when people can't do things that they want to do when they want to.
>
> Indeed. It's supposed to be simple to transfer files via Bluetooth (and
> probably WiFi),
The problem I have with Bluetooth is that the "secret codes" are a PITA.
<
https://i.postimg.cc/JhjpnRgh/webdav14.jpg> Mirroring Android on Windows
> and I didn't have problems linking my phone and laptop -
> it's just that they didn't want to talk to each other! I wouldn't be
> surprised if there are some permissions issues going on (see my comment
> about 6-digit pairing numbers below). Anyway, now the USB transfer has
> been re-established, I /might/ revisit Bluetooth to see if I can get it
> working.
I find the "security" of Bluetooth a PITA, where I think you'll like WebDAV
better since it mounts the Android filesys as a Windows drive letter.
<
https://i.postimg.cc/yYWwgGmy/webdav12.jpg> Android Windows drive letters
>> There are other ad hoc methods we've discussed on this ng in the past,
>> e.g.,
>> a. NitroShare
>
> FYI I had a look at the Play Store, but was informed that Nitroshare
> wasn't available as it only worked with an earlier version of Android.
Hmmmm... haven't needed NitroShare in a long time as I used it when I
tested _every single suggestion_ for filesharing ever made on this ng.
<
https://nitroshare.net/>
I think you may be confusing the "server" with the "client" though.
<
https://play.google.com/store/apps/details?id=net.nitroshare.android>
Here are the screenshots from my last test using Nitroshare on my Android.
<
https://i.postimg.cc/90HqTpw2/nitroshare01.jpg> Open Windows firewall
<
https://i.postimg.cc/Z5382rkR/nitroshare02.jpg> Android NitroShare
<
https://i.postimg.cc/CMzvhP9r/nitroshare03.jpg> Select file(s)
<
https://i.postimg.cc/qBsN34fN/nitroshare04.jpg> Select desktop
>> b. KDE Connect
>
> Looks best for me as it's installed by default on Linux Mint. However,
> it seems I might have to do something to allow access via any firewall I
> have on the laptop.
As I said, I've tested _every_ suggested file-sharing solution on this ng.
<
https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp>
Here are my screenshots from when I had tested KDE Connect with Windows.
<
https://i.postimg.cc/qqcHvN6T/kdeconnect01.jpg> KDEConnect setup
<
https://i.postimg.cc/ZYHf4PCq/kdeconnect02.jpg> KDEConnect pairing
<
https://i.postimg.cc/cJ39SVnq/kdeconnect03.jpg> KDEConnect sharing
>> c. Kies (works on more than just Samsung)
>> etc.
>
> Yes, there are quite a few file transfer apps, but some require a
> careful looking at.
Agreed. There are a billion file-sharing apps.
I've tested ever free app which has been suggested on this newsgroups.
That's scores of them.
Including SMB/Cifs/Samba & FTPUSe for example (which Frank knows about).
Most aren't worth using.
USB and Wi-Fi and WebDav are the ones I'd concentrate on.
Personally, I'd not use Bluetooth.
Too much of a PITA in the authentication process.
> One of the first ones I installed to try out asked
> immediately for location access so it could detect any nearby devices to
> transfer or receive files to/from. That's the problem with the Play
> Store - there's very little information to go on.
If you search for my step-by-step tutorials, you'll find what you need.
>> One thing you can doublecheck on the phone is the USB setting of course.
>> <
https://i.postimg.cc/JnDTWH9M/usb01.jpg> USB default settings
>> Yes. I know you checked it. Look in the Developer options to make sure.
>
> That's interesting. There was no "Developer options" available under
> "Settings" on my phone, until I found out how to reveal it just now.
We've discussed Developer options so many times to explain how to enable it
would sort of be like explaining how to open the Windows registry editor.
People all know about it by now if they've been on this ng for a while.
> When I looked at "Default USB configuration" it had "No data transfer".
> If that's the case, as I was able to do it previously, it must have
> changed during an update. I've changed it to "File transfer".
I would leave it forever at that setting and never worry about it again.
>> Both adb and termux can both copy files over Wi-Fi without USB.
>> <
https://i.postimg.cc/ZK9B82gP/adb15.jpg> adb pair [IP][Port] [code]
>> <
https://i.postimg.cc/SRRXtvKh/adb16.jpg> Android 12 Wireless Pairing
>
> Aha!. I'd noticed those 6-digit numbers appearing and there was a
> comment that they weren't available (or something similar). Now I know
> what they were - to pair with the device! Android can be less than
> informative...
This pairing is what makes Wi-Fi transfer more of a PITA than USB cable.
I use adb all day, every day - but it still is a PITA to have to pair it
which is why lately I've been using adb over USB more than adb over Wi-Fi.
<
https://i.postimg.cc/9M0Tqzm6/adb01.jpg> Wireless debugging option
<
https://i.postimg.cc/hPVtkTXK/adb02.jpg> Boot turns W/L debug off
<
https://i.postimg.cc/Dyy7rWYd/adb03.jpg> Activity requires permission
<
https://i.postimg.cc/wTfg06CK/adb04.jpg> WiFi Calling on/off Activity
<
https://i.postimg.cc/Gm4rfWR4/adb05.jpg> Some Activities fail to run
<
https://i.postimg.cc/3xz7Qtrn/adb06.jpg> Run Activity from Termux
<
https://i.postimg.cc/W3vvhtkZ/adb07.jpg> Activity = Bad Component Name
<
https://i.postimg.cc/9X1hQmF4/adb08.jpg> Starting Intent with -n
<
https://i.postimg.cc/zB5sqMsS/adb09.jpg> Same Intent different name
<
https://i.postimg.cc/rwb9Mrr8/adb10.jpg> WiFi settings overview
<
https://i.postimg.cc/xTqWjL47/adb11.jpg> WiFi control history
<
https://i.postimg.cc/R0x8TyZ5/adb12.jpg> Using an Activity Inspector
<
https://i.postimg.cc/7hhQ6ym7/adb13.jpg> Adb using -a for wifi Intents
<
https://i.postimg.cc/sxn4F1WS/adb14.jpg> Wi-Fi Calling Activity
<
https://i.postimg.cc/CLWZmJT3/adb17.jpg> Allow wireless debugging
<
https://i.postimg.cc/rmBHmvtV/adb18.jpg> Windows adb vysor & scrcpy
<
https://i.postimg.cc/CLyK8z9v/adb20.jpg> Both vysor & scrcpy use adb
<
https://i.postimg.cc/qRhkhTwV/adb21.jpg> Android Wireless-debugging tile
<
https://i.postimg.cc/zfLp8b2v/adb22.jpg> Windows Ctrl-Z,bg workaround
<
https://i.postimg.cc/85FwbwfX/adb23.jpg> USB needed before Android 11
<
https://i.postimg.cc/SRBWNrJ3/adb24.jpg> Android 12 needs no USB
<
https://i.postimg.cc/6p90PBGv/adb25.jpg> C:\> set ANDROID_ADB_SERVER_PORT
<
https://i.postimg.cc/YjBWwCPw/adb26.jpg> setprop service.adb.tcp.port #
<
https://i.postimg.cc/L4bDbk6z/adb27.jpg> scrcpy --tcpip=[IP]:[PORT]
<
https://i.postimg.cc/zDCTY9NS/adb28.jpg> multiple adb connections
<
https://i.postimg.cc/R0BXTMCy/adb29.jpg> multiple pairing connections
<
https://i.postimg.cc/DZV4tcYM/adb30.jpg> Windows pairing debuggers
<
https://i.postimg.cc/436FCYFX/adb31.jpg> Local adb runs on Android
<
https://i.postimg.cc/7YLhtcZL/adb32.jpg> ladb eliminates the PC
<
https://i.postimg.cc/9MSg3sjj/adb33.jpg> Long and short serial formats
It's basically any Linux distro that you want, running on unrooted Android.
It's alongside of Android - so it's just additive.
<
https://play.google.com/store/apps/details?id=studio.com.techriz.andronix>
You use it when you need it.
Just like you do with Termux.
>> Good that you're using Marcel's tool - he's a sensitive person who would
>> love if you send him a message of thanks - he's VERY sensitive about it.
>
> It is a very good app, but even in its free form is powerful and quite
> complicated.
Let Marcel know if you can.
I've helped him test it, especially when Google tried to screw him over.
He fixed everything I needed fixing.
There's never a need to use the GMail app (which creates an account).
>> Sometimes just a simple reboot is "magic" with computers. Don't ask me why.
>
> Isn't it the basic operating method when using Windows? ;-)
Only with computers is doing the same thing twice and expecting a different
outcome that second time not the definition of crazy.
>> Glad you got it sorted out.
>
> Thanks for your help and advice once again. I'm (very slowly...) getting
> there.
I'm different than most posters in this newsgroup as I'm not here for
amusement. I'm here to help others (and to learn from them).
--
And, when iOS is involved - to show the iKooks for what they really are.